BlueCielo Meridian Enterprise 2012 Administrator's Guide | BlueCielo ECM Solutions

You are here: BlueCielo Meridian Enterprise Administrator's Guide > About Meridian network administration > About Meridian support for Microsoft Active Directory > Using Meridian with multiple domains > Configuring NetBIOS name resolution

Configuring NetBIOS name resolution

If user access problems still occur after configuring the Meridian service account as described in Granting membership query access. the problem could be caused by incorrect NetBIOS name resolution.

Note    You can confirm this cause by testing whether vault access works for the remote domain users as long as no roles are applied in the vault. You can also test this by creating a temporary test vault. As soon as roles are applied to the vault, users in remote domains can no longer access the vault. Only users from the home domain (the domain where the Meridian application server resides) can access the vault.

If the Meridian application server is not able to find a domain controller for the remote domain, add the remote domain to the DNS suffix list for the TCP/IP protocol of the Meridian application server’s active network card.

Other conditions that can cause this behavior include:

Related concepts

About Meridian support for Microsoft Active Directory

Understanding Active Directory security problems

Understanding DCOM problems

Using Meridian with nested groups

Using Meridian with multiple domains

Related tasks

Granting domain privileges with a service account

Granting domain privileges to the Meridian server

Enabling DCOM

Configuring DCOM permissions

Granting membership query access

Running BlueCielo License Server on a different computer

NEW  Synchronizing user groups with Active Directory


Copyright © 2000-2012 BlueCielo ECM Solutions

www.bluecieloecm.com